Documentation Center

Experience Optimization file system permissions on presentation side

This topic lists the file system settings for Experience Optimization and Fredhopper running on the presentation side. It is assumed that the permissions are inherited in all subfolders and only overridden in a subfolder if it is specifically listed.

User accountDescription
WebUsersThe user of your Web site, for example IUSR for anonymous users in IIS.
LocationAccess levelReason
C:\ (Windows only)All users require Read access.Proper system functionality (instantiate objects, open folders)
Web site foldersRead and Execute access for WebUsers.Needed to access the pages on your Web site.
%TRIDION_HOME%\config or %WEBSITE%\configRead access for the following users: stuser and stdeployerReading of configuration files.
%TRIDION_HOME%\lib or %WEBSITE%\libRead access for the following users: stuser and stdeployerCalling the Experience Optimization and Content Delivery APIs.
Log directory (configurable)Write access for the following users: stuser and stdeployerLog files are stored here (as configured in logback.xml).
Google Analytics Private Key directory

(The location of the P12 Key generated when you set up your Project)

Read access for WebUsers

(For Experience Optimization Web service and Web site)

For the Web site to collect and store statistics associated with this project.

For the Experience Optimization Web service to retrieve and display statistics in Targeting Dashboard.

Java executable (\bin)Read and Execute access for the following users: stuser and stdeployerNeeded to run the Java code (including .NET Web sites).
JRE / runtime librariesRead access for the following users: stuser and stdeployerNeeded to run the Java code (including .NET Web sites).
In the following table:
  • <BASE_DIRECTORY> refers to the root directory of your Fredhopper Deployment Package, for example C:\fredhopper
  • <INDEXER> refers to the name of your Index Server in the case of <BASE_DIRECTORY>\<INDEXER>, or the root if of your Index Server, for example <BASE_DIRECTORY>\data\instances\SmartTargetIndexer (as specified in the topology.txt file )
  • catalog01 refers to the name of your universe
LocationAccess levelReason
<BASE_DIRECTORY>Read access for fhuser.Proper functioning of Fredhopper.
<BASE_DIRECTORY>\dataRead and Modify access for fhuser.Data directory used by the Business Manager and the different Fredhopper processes.
<BASE_DIRECTORY>\<INDEXER>\data\fas-xml-incremental\catalog01Write access for stdeployer.

Read and Modify access for fhuser.

Used to deploy Component Presentations to Fredhopper when content is published. The Fredhopper processes will move files from this directory into the \processed directory.
<INDEXER>Read access for stdeployer.Proper functioning of Experience Optimization.
<INDEXER>\log

Write access for fhuser.

Fredhopper log files are written to this location.
<INDEXER>\tmp

Read and Modify access for fhuser.

Temporary files are created in this location.
<INDEXER>\configRead and Modify access for fhuser.Contains all configuration files for the instance, for example the business.xml, trigger-types.xml and localization files.
<INDEXER>\tomcat

Read and Modify access for fhuser.

Business Manager runs in a Tomcat instance. It will deploy applications and create temp files and directories as part of its functionality.